Apparatus and method for providing interactive service to device using different digital broadcast middleware standards

ABSTRACT

An apparatus and method for providing an interactive service to devices using different digital broadcast middleware standards are provided. The apparatus includes an execution information providing module which provides execution information regarding an application that has been executed in a first device using a first middleware standard so that the application can be executed in a second device using a second middleware standard; and a request execution module which receives a request issued by the second device during the execution of the application in the second device, and performs an operation corresponding to the received request.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application claims priority from Korean Patent Application No.10-2007-0016157, filed on Feb. 15, 2007 in the Korean IntellectualProperty Office, the disclosure of which is incorporated herein byreference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

Apparatuses and methods consistent with the present invention relate toproviding an interactive service to devices using different digitalbroadcast middleware standards, and more particularly, to providing aninteractive service to devices with different digital cable broadcastmiddleware standards without modification of existing specifications.

2. Description of the Related Art

Cable broadcasting is increasingly expected not only to be able toprovide high-quality two-way services, but also to become a mostsuitable medium in the near future for broadcast/communicationintegrated services due to its capabilities to provide two-way services,achieve high transmission speeds and transmit considerable amounts ofdata.

In order to realize two-way digital cable broadcast services, set-topboxes (STBs), which are control boxes for receiving broadcast programsand performing various additional functions, are necessary.

STBs can provide bidirectionality to broadcasting, and are essential forthe reception of digital broadcast programs with high picture qualityand high sound quality and for the realization of two-way services.Thus, the importance of STBs to digital broadcasting has grown steadily.

Before the full implementation of digital broadcasting, a broadcastreception function used to be one of the main functions of STBs.However, with the digitalization of STBs, STBs have evolved into digitalconsumer devices that are capable of providing not only a broadcastreception function but also a variety of additional functions such as acommunication function, a personal video recorder (PVR) function, and anelectronic program guide (EPG) function.

OpenCable is a digital cable broadcast standard which includes bothhardware and software specifications.

A hardware implementation of OpenCable includes an STB and a point ofdeployment (POD) module which separates conditional access/securityfunctions from the STB, and a software implementation of OpenCable isOpenCable Applications Platform (OCAP), which is a middlewarespecification.

More specifically, OCAP is a standard for developing two-wayapplications. OCAP can provide web-based services for digital cablebroadcasting and can thus support further advanced two-way services forviewers. OpenCable devices use the same middleware platform called OCAPand can thus share application software and content with one another.

High Definition Audio Video Network Alliance (HANA) has proposed asolution for connecting a built-in digital television (DTV) and one ormore peripheral devices via IEEE 1394 so that the DTV and the peripheraldevices can be controlled in an integrated manner, and thathigh-definition (HD) content can be shared between the DTV and theperipheral device. The HANA solution involves the use of a DTV equippedwith a decoder and a web browser and a peripheral device equipped with aweb server and a control page.

The HANA solution can enable a DTV to decode digital broadcast signalsand HD content present in peripheral devices and can control theperipheral devices in an integrated manner using a web browser of theDTV as a graphic user interface (GUI).

The HANA solution can control all devices connected to an IEEE 1394network using a single integrated remote control.

According to the HANA solution, EPG information, paper per view (PPV)data, video on demand (VOD) data, and shopping programs are transmittedbetween a HANA system including a HANA DTV, a television (TV) node, anaudio/video (A/V) hard disc drive, and a HANA eXtended Home Theater(XHT) STB cable network interface unit (NIU), and an XHT STB asHypertext Markup Language (HTML) data, and user interfaces (UIs) aredisplayed in the HANA system and the XHT STB as HTML data.

If an OpenCable STB connected to a HANA system via IEEE 1394 is equippedwith OCAP middleware, applications that are executed using MultimediaHome Platform (MHP) or OCAP middleware may not be provided as HTML data,and thus may not be able to be directly applied to the HANA system. Inorder for an IEEE 1394-based HANA system to utilize OCAP-basedinteractive services, an extension to the OCAP specification isrequired.

Applications for providing UIs for a HANA system and providing UIs forusers and various HANA applications may be executed using a web browserincluded in an HTML-based HANA DTV.

The OCAP 1.0 specification provides Java-based applications, calledOCAP-J applications, and Java-based UIs. OCAP-J applications, however,cannot be executed using a web browser of a HANA DTV.

SUMMARY OF THE INVENTION

The present invention provides an apparatus and method for providing aninteractive service to devices using different digital broadcastmiddleware standards which can enable devices that comply with the HANAspecification to utilize OCAP applications.

According to an aspect of the present invention, there is provided anapparatus for providing an interactive service to devices usingdifferent digital broadcast middleware standards, the apparatusincluding an execution information providing module which providesexecution information regarding an application that has been executed ina first device using a first middleware standard so that the applicationcan be executed in a second device using a second middleware standard;and a request execution module which receives a request issued by thesecond device during the execution of the application in the seconddevice, and performs an operation corresponding to the received request.

According to another aspect of the present invention, there is providedan apparatus for providing an interactive service to devices usingdifferent digital broadcast middleware standards, the apparatusincluding an application execution module which is provided withexecution information regarding an application that has been executed ina first device using a first middleware standard and which executes theapplication in a second device using a second middleware standard withreference to the execution information, a request module which issues arequest to the first device during the execution of the application inthe second device, and a display module which displays the result of theexecution of the application in the second device.

According to another aspect of the present invention, there is provide amethod providing an interactive service to devices using differentdigital broadcast middleware standards, the method including providingexecution information regarding an application that has been executed ina first device using a first middleware standard so that the applicationcan be executed in a second device using a second middleware standard,and receiving a request issued by the second device during the executionof the application in the second device, and performing an operationcorresponding to the received request.

According to another aspect of the present invention, there is provide amethod of providing an interactive service to devices using differentdigital broadcast middleware standards, the method including receivingexecution information regarding an application that has been executed ina first device using a first middleware standard and executing theapplication in a second device using a second middleware standard withreference to the execution information, issuing a request to the firstdevice during the execution of the application in the second device, anddisplaying the result of the execution of the application in the seconddevice.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects of the present invention will become moreapparent by describing in detail exemplary embodiments thereof withreference to the attached drawings in which:

FIG. 1 is a block diagram of a system for providing an interactiveservice to devices using different digital broadcast middlewarestandards according to an exemplary embodiment of the present invention;

FIG. 2 is a block diagram of an apparatus for providing an interactiveservice to devices using different digital broadcast middlewarestandards according to an exemplary embodiment of the present invention;

FIG. 3 is a block diagram of an apparatus for providing an interactiveservice to devices using different digital broadcast middlewarestandards according to another exemplary embodiment of the presentinvention;

FIG. 4 is a flowchart illustrating a method of providing an interactiveservice to devices using different digital broadcast middlewarestandards according to an exemplary embodiment of the present invention;and

FIG. 5 is a flowchart illustrating a method of providing an interactiveservice to devices using different digital broadcast middlewarestandards according to another exemplary embodiment of the presentinvention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS OF THE INVENTION

The present invention will now be described more fully with reference tothe accompanying drawings, in which exemplary embodiments of theinvention are shown. The invention may, however, be embodied in manydifferent forms and should not be construed as being limited to theexemplary embodiments set forth herein; rather, these exemplaryembodiments are provided so that this disclosure will be thorough andcomplete, and will fully convey the concept of the invention to thoseskilled in the art. Like reference numerals in the drawings denote likeelements, and thus their description will be omitted.

The present invention is described hereinafter with reference toflowchart illustrations of user interfaces, methods, and computerprogram products according to exemplary embodiments of the invention. Itwill be understood that each block of the flowchart illustrations, andcombinations of blocks in the flowchart illustrations, can beimplemented by computer program instructions. These computer programinstructions can be provided to a processor of a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which are executed via the processor of the computer or otherprogrammable data processing apparatus, create means for implementingthe functions specified in the flowchart block or blocks.

These computer program instructions may also be stored in a computerusable or computer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer usable orcomputer-readable memory produce an article of manufacture includinginstruction means that implement the function specified in the flowchartblock or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions that are executed on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Each block of the flowchart illustrations may represent a module,segment, or portion of code, which comprises one or more executableinstructions for implementing the specified logical function(s). Itshould also be noted that in some alternative implementations, thefunctions noted in the blocks may occur out of the order. For example,two blocks shown in succession may in fact be executed substantiallyconcurrently or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved.

FIG. 1 is a block diagram of a system for providing an interactiveservice to devices with digital broadcast middleware standards accordingto an exemplary embodiment of the present invention. Referring to FIG.1, the system is designed for executing distributed OCAP applications sothat OCAP applications can be executed in HANA DTVs without anymodification to existing OCAP standard specifications.

Referring to FIG. 1, in order to execute an OCAP user interface or anOCAP application in a HANA DTV 120, an OCAP network interface unit (NIU)110 may include a distributed OCAP application server (DOAS) 111, andthe HANA DTV 120 may include a distributed OCAP client copy (DOCC) 121.

The HANA DTV 120 may also include an extended resource support package(ERSP) 122 for accessing graphic resources, MPEG-2 transport stream (TS)decoders, and A/V display resources. Therefore, an OCAP interactiveservice can be provided to the OCAP NIU 110 and the HANA DTV 120 whichis connected to the OCAP NIU 110 via an HANA 1394 network.

In order to execute the DOAS 111 and the DOCC 121, a distributed OCAPenvironment library (DOEL) for a primitive running environment may beprovided.

The DOAS 111, the DOCC 121, and the ERSP 122 will hereinafter bedescribed in further detail with reference to FIGS. 2 and 3.

FIG. 2 is a block diagram of an apparatus 200 for providing aninteractive service to devices using different digital broadcastmiddleware standards according to an exemplary embodiment of the presentinvention. Referring to FIG. 2, assuming that there are first and seconddevices using different digital broadcast middleware standards, i.e.,use first and second middleware standards, respectively, the apparatus200 includes an execution information providing module 201 whichprovides execution information regarding an application that has beenexecuted in the first device using the first middleware standard so thatthe application can also be executed in the second device using thesecond middleware standard; and a request execution module 202 whichreceives a request from the second device during the execution of theapplication in the second device and performs an operation correspondingto the received request.

FIG. 3 is a block diagram of an apparatus 300 for providing aninteractive service to devices using different digital broadcastmiddleware standards according to another exemplary embodiment of thepresent invention. Referring to FIG. 3, the apparatus 300 includes anapplication execution module 301 which is provided with executioninformation regarding an application that has been executed in the firstdevice by the first device and executes the application in the seconddevice with reference to the execution information; a request module 302which issues a request to the first device during the execution of theapplication in the second device; and a display module 303 whichdisplays the result of executing the application in the second device inthe second device.

The term ‘module’, as used herein, means, but is not limited to, asoftware or hardware component, such as a Field Programmable Gate Array(FPGA) or Application Specific Integrated Circuit (ASIC), which performscertain tasks. A module may advantageously be configured to reside onthe addressable storage medium and configured to execute on one or moreprocessors. Thus, a module may include, by way of example, components,such as software components, object-oriented software components, classcomponents and task components, processes, functions, attributes,procedures, subroutines, segments of program code, drivers, firmware,microcode, circuitry, data, databases, data structures, tables, arrays,and variables. The functionality provided for in the components andmodules may be combined into fewer components and modules or furtherseparated into additional components and modules.

For purposes of explanation, it will be assumed that the apparatus 200illustrated in FIG. 2 is included in the first device, and that theapparatus 300 illustrated in FIG. 3 is included in the second device.

Referring to FIG. 2, the execution information providing module 201provides execution information regarding an application that has beenexecuted in the first device using the first middleware standard so thatthe application can also be executed in the second device using thesecond middleware standard.

The first device may include OCAP middleware, and an application or auser interface (UI) that satisfies the OCAP standard may be executed inthe first device.

The OCAP application executes at least one of a cable card, a Data OverCable Service Interface Specification (DOCSIS) set-top gateway (DSG)module, a tuner, a demultiplexer, and an IEEE 1394 interface that areall installed in the first device. Here, the DSG transmits data using acable modem. The execution information may include at least one of anOCAP unbound application, an OCAP Xlet, an application information table(AIT), an extended AIT (XAIT), system information (SI), and programsystem information protocol (PSIP) for executing, in the second device,an OCAP UI or an OCAP application that has been executed in the firstdevice.

The execution information is needed for remote execution of the OCAPapplication in the second device. The first device may serve as a serverby providing the second device with the execution information.

The OCAP application may be classified as a bound application or anunbound application. Information regarding the OCAP application may beprovided as an AIT for a bound application or an XAIT for an unboundapplication by a head end. The execution information providing module201 may be included in the first device. The execution informationproviding module 201 parses information present in the AIT or the XAITprovided by the head end, classifies the parsed information intoapplication information regarding a tuner or a cable card to be executedin the first device and application information regarding a UI or a Javaapplication, and provides the application information regarding a UI ora Java application to the second device.

The second device may execute an application with reference to theexecution information provided by the execution information providingmodule 201. In this case, the second device may issue a request to thefirst device during the execution of an application in the seconddevice, and the request execution module 202 in the first device mayreceive the request issued by the second device and execute a commandcorresponding to the received request.

The execution information providing module 201 and the request executionmodule 202 may be included in the DOAS 111 illustrated in FIG. 1.

The second device may include CEA-2027 middleware that involves XHTtechnology. The second device may include one or more HANA DTVs.

The request issued by the second device may be a request forchannel-tuning for an application currently being executed by the seconddevice or a request for an MPEG TS, SI data, PSI data, or informationregarding at least one of a tuner, an out-of-band (OOB) channel, OOBreceiver/transmitter, a persistent storage, section filters, conditionalaccess system (CAS) messaging, a cable card, and object carousels to beexecuted in the first device.

The request execution module 202 receives the request issued by thesecond device, manages an AIT and conditions for the maintenance andtermination of a bound application, exchanges an OCAP call for remoteexecution with the second device as a message, and enables the firstdevice and the second device to operate in connection with each other.

Referring to FIG. 3, the application execution module 301 is providedwith execution information regarding an application that has beenexecuted in the first device and executes the application in the seconddevice with reference to the execution information.

The first device may include OCAP middleware, and an application or a UIthat satisfies the OCAP standard may be executed in the first device.

The second device may include CEA-2027A or CEA-931B middleware thatinvolves XHT technology. The second device may include one or more HANADTVs.

An OCAP application and execution information have already beendescribed above with reference to FIG. 2, and thus, detaileddescriptions thereof will be omitted.

The application execution module 301 may be provided with executioninformation regarding an application as a jar file by the first device,and executes all OCAP applications in devices such as HANA DTVs.

In this case, the application execution module 301 may be provided witha copy of an OCAP application by the execution information providingmodule 201 of the apparatus 200 illustrated in FIG. 2. Morespecifically, the execution information providing module 201 parsesinformation present in an AIT or an XAIT, classifies the parsedinformation into application information regarding a tuner or cable cardto be executed in the first device and application information regardinga UI or a Java application, and provides the application informationregarding a UI or a Java application to the second device.

Referring to FIG. 1, even if two or more HANA DTVs are connected to theOCAP NIU 110 via a network, the DOAS 111 can execute a plurality ofDOCCs respectively copied to the HANA DTVs so that an OCAP applicationcan be executed in each of the HANA DTVs.

In this manner, various applications selected by a user, for example,monitor applications, electronic program guide (EPG) data, OCAP boundapplications and OCAP unbound applications, can be executed in devicessuch as HANA DTVs.

The request module 302 issues a request to the first device during theexecution of an application in the second device. The request issued bythe request module 302 has already been described above with referenceto FIG. 2, and thus, a detailed description thereof will be skipped.

The application execution module 301 and the request module 302 may beincluded in the DOCC 121 illustrated in FIG. 1.

The display module 303 displays an OCAP UI or an OCAP application thathas been executed in the second device.

For this, the display module 303 maps an org.dvb.* package, i.e., anERSP, which is a set of classes that are implemented in connection withan OCAP UI and a media play by using native code or Java, to resourcesfor executing the ERSP in a HANA DTV.

For example, in order to execute a JAVA UI application in a personalcomputer (PC), functions for drawing lines on a JAVA UI must be mappedto primitive code provided by a graphic and display application of a PCfor drawing lines. Given all this, the display module 303 provides anERSP for mapping primitive codes of a graphic and display system forcontrolling lines displayed on the screen of a HANA DTV or pixels on thescreen of a HANA DTV to various functions in an application.

The display module 303 may include the ERSP 122 illustrated in FIG. 1.

The above-mentioned mapping process may be necessary for realizingfunctions such as ‘play’ and ‘stop’ in a Java Media Framework (JMF)which can process time-based media such as audio and video packages, andthese functions may be provided by an ERSP.

FIG. 4 is a flowchart illustrating a method of providing an interactiveservice to devices using different digital broadcast middlewarestandards according to an exemplary embodiment of the present invention.For convenience, the method illustrated in FIG. 4 will hereinafter bedescribed in detail with reference to FIGS. 2 and 3.

Referring to FIG. 4, in operation S401, the execution informationproviding module 201 of the apparatus 200 illustrated in FIG. 2 providesexecution information regarding an application that has been executed ina first device using a first middleware standard so that the applicationcan also be executed in a second device using a second middlewarestandard.

The first device may include OCAP middleware. An application or a UIthat satisfies the OCAP standard may be executed in the first device.

The OCAP application executes at least one of a cable card, a DSG, atuner, a demultiplexer, and an IEEE 1394 interface which are allinstalled in the first device. Here, the DSG transmits data using acable modem. The execution information may include at least one of anOCAP unbound application, an OCAP Xlet, an AIT, an XAIT, SI, and PSIPfor executing, in the second device, an OCAP UI or an OCAP applicationthat has been executed in the first device.

The execution information is needed for remote execution of the OCAPapplication in the second device. The first device may serve as a serverby providing the second device with the execution information.

In response to receiving the execution information, the second deviceexecutes the OCAP application with reference to the executioninformation, and issues a request to the first device during theexecution of the OCAP application.

In operation S402, the request execution module 202 receives the requestissued by the second device.

In operation S403, the request execution module 202 executes a commandcorresponding to the received request.

The second device may include CEA-2027A or CEA-931B middleware thatinvolves XHT technology. The second device may include one or more HANADTVs.

The received request may be a request for channel-tuning for the OCAPapplication currently being executed by the second device or a requestfor an MPEG TS, SI data, PSI data, or information regarding at least oneof a tuner, an out-of-band (OOB) channel, an OOB receiver/transmitter, apersistent storage, section filters, conditional access system (CAS)messaging, a cable card, and object carousels to be executed in thefirst device.

In operation S404, the request execution module 202 manages an AIT andconditions for the maintenance and termination of a bound application inresponse to the received request, exchanges an OCAP call for remoteexecution with the second device as a message, and enables the firstdevice and the second device to operate while connected with each other.

FIG. 5 is a flowchart illustrating a method of providing an interactiveservice to devices using different digital broadcast middlewarestandards according to another exemplary embodiment of the presentinvention. Referring to FIG. 5, in operation S501, the applicationexecution module 301 of the apparatus 300 illustrated in FIG. 3 receivesexecution information regarding an application that has been executed inthe first device. In operation S502, the second device executes anapplication with reference to the execution information.

Here, the first device may include OCAP middleware, and an applicationor a UI that satisfies the OCAP standard may be executed in the firstdevice.

The second device may include CEA-2027A or CEA-931B middleware thatinvolves XHT technology. The second device may include one or more HANADTVs.

An application and execution information have already been describedabove with reference to FIG. 2, and thus, detailed descriptions thereofwill be skipped.

The application execution module 301 may be provided with executioninformation regarding an application as a jar file by the first device,and executes all OCAP applications in devices such as HANA DTVs.

In this case, the application execution module 301 may be provided witha copy of an OCAP application by the execution information providingmodule 201 of the apparatus 200 illustrated in FIG. 2. Morespecifically, the execution information providing module 201 parsesinformation present in an AIT or an XAIT, classifies the parsedinformation into application information regarding a tuner or cable cardto be executed in the first device and application information regardinga UI or a Java application, and provides the application informationregarding a UI or a Java application to the second device.

Referring to FIG. 1, even if two or more HANA DTVs are connected to theOCAP NIU 110 via a network, the DOAS 111 can execute a plurality ofDOCCs respectively copied to the HANA DTVs so that an OCAP applicationcan be executed in each of the HANA DTVs.

In this manner, various applications selected by a user, for example,monitor applications, electronic program guide (EPG) data, OCAP boundapplications and OCAP unbound applications, can be executed in devicessuch as HANA DTVs.

In operation S503, the request module 302 issues a request to the firstdevice during the execution of an application in the second device. Therequest issued by the request module 302 has already been describedabove with reference to FIG. 1, and thus, a detailed description thereofwill be skipped.

In operation S504, the display module 303 displays an OCAP UI or an OCAPapplication that has been executed in the second device.

For this, the display module 303 maps an org.dvb.* package, i.e., anERSP, which is a set of classes that are implemented in connection withan OCAP UI and a media play by using native code or Java, to resourcesfor executing the ERSP in a HANA DTV.

The apparatus and method for providing an interactive service to devicesusing different digital broadcast middleware standards according to thepresent invention have the following advantages.

First, it is possible to promote the commercialization of the HANA XHTstandard by enabling HANA devices (such as HANA DTVs) as well asOpenCable devices (such as OCAP cable NIUs) equipped with the OCAP 1.0specification to receive OCAP-based broadcast services.

Second, it is possible to share A/V data between devices that areconnected via a home network by interlinking OCAP-based interactiveservices provided by a head end with HANA solutions.

While the present invention has been particularly shown and describedwith reference to exemplary embodiments thereof, it will be understoodby those of ordinary skill in the art that various changes in form anddetails may be made therein without departing from the spirit and scopeof the present invention as defined by the following claims.

1. An apparatus for providing an interactive service to devices whichutilize different digital broadcast middleware standards, the apparatuscomprising: an execution information providing module which providesexecution information regarding an application that has been executed ina first device using a first middleware standard so that the applicationcan be executed in a second device using a second middleware standard;and a request execution module which receives a request issued by thesecond device during execution of the application in the second device,and performs an operation corresponding to the request which isreceived.
 2. The apparatus of claim 1, wherein the first devicecomprises OpenCable Application Platform middleware.
 3. The apparatus ofclaim 1, wherein the application executes at least one of a cable card,a Data Over Cable Service Interface Specification set-top gatewaymodule, and a tuner that are installed in the first device.
 4. Theapparatus of claim 1, wherein the execution information comprises atleast one of a copy of the application, an application information table(AIT), an extended AIT, system information, and program systeminformation protocol.
 5. The apparatus of claim 4, wherein the executioninformation is utilized for remote execution of the application in thesecond device.
 6. The apparatus of claim 1, wherein the second devicecomprises CEA-2027A or CEA-931B middleware that utilizes Extended HomeTheater technology.
 7. The apparatus of claim 6, wherein the seconddevice comprises at least one High Definition Audio Video NetworkAlliance digital television.
 8. The apparatus of claim 1, wherein therequest comprises a request for channel tuning for the application or arequest for at least one of an MPEG transport stream, system informationdata, and program system information data.
 9. An apparatus for providingan interactive service to devices which utilize different digitalbroadcast middleware standards, the apparatus comprising: an applicationexecution module which receives execution information regarding anapplication that has been executed in a first device using a firstmiddleware standard, and which executes the application in a seconddevice using a second middleware standard with reference to theexecution information; a request module which issues a request to thefirst device during execution of the application in the second device;and a display module which displays a result of the execution of theapplication in the second device.
 10. The apparatus of claim 9, whereinthe first device comprises OpenCable Application Platform middleware.11. The apparatus of claim 9, wherein the application executes at leastone of a cable card, a Data Over Cable Service Interface Specificationset-top gateway module, and a tuner that are installed in the firstdevice.
 12. The apparatus of claim 9, wherein the execution informationcomprises at least one of a copy of the application, an applicationinformation table (AIT), an extended AIT, system information, andprogram system information protocol.
 13. The apparatus of claim 12,wherein the execution information is utilized for remote execution ofthe application in the second device.
 14. The apparatus of claim 9,wherein the second device comprises CEA-2027A or CEA-931B middlewarethat utilizes Extended Home Theater technology.
 15. The apparatus ofclaim 14, wherein the second device comprises at least one HighDefinition Audio Video Network Alliance digital television.
 16. Theapparatus of claim 9, wherein the application execution module managesat least one of download of the application, the execution of theapplication in the second device, and termination of the execution ofthe application in the second device.
 17. The apparatus of claim 9,wherein the request comprises a request for channel tuning for theapplication or a request for at least one of an MPEG transport stream,system information data, and program system information protocol data.18. A method providing an interactive service to devices which utilizedifferent digital broadcast middleware standards, the method comprising:providing execution information regarding an application that has beenexecuted in a first device using a first middleware standard so that theapplication can be executed in a second device using a second middlewarestandard; and receiving a request issued by the second device duringexecution of the application in the second device, and performing anoperation corresponding to the request which is received.
 19. The methodof claim 18, wherein the first device comprises OpenCable ApplicationPlatform middleware.
 20. The method of claim 18, wherein the applicationexecutes at least one of a cable card, a Data Over Cable ServiceInterface Specification set-top gateway module, and a tuner that areinstalled in the first device.
 21. The method of claim 18, wherein theexecution information comprises at least one of a copy of theapplication, an application information table (AIT), an extended AIT,system information, and program system information protocol.
 22. Themethod of claim 21, wherein the execution information is utilized forremote execution of the application in the second device.
 23. The methodof claim 18, wherein the second device comprises CEA-2027A or CEA-931Bmiddleware that utilizes XHT technology.
 24. The method of claim 23,wherein the second device comprises at least one High Definition AudioVideo Network Alliance digital television.
 25. The method of claim 18,wherein the request comprises a request for channel tuning for theapplication or a request for at least one of an MPEG transport stream,system information data, and program system information data.
 26. Amethod of providing an interactive service to devices which utilizedifferent digital broadcast middleware standards, the method comprising:receiving execution information regarding an application that has beenexecuted in a first device using a first middleware standard, andexecuting the application in a second device using a second middlewarestandard with reference to the execution information; issuing a requestto the first device during the executing the application in the seconddevice; and displaying the application in the second device displaying aresult of the executing of the application in the second device.
 27. Themethod of claim 26, wherein the first device comprises OpenCableApplication Platform middleware.
 28. The method of claim 26, wherein theapplication executes at least one of a cable card, a Data Over CableService Interface Specification set-top gateway module, and a tuner thatare installed in the first device.
 29. The method of claim 26, whereinthe execution information comprises at least one of a copy of theapplication, an application information table (AIT), an extended AIT,system information, and program system information protocol.
 30. Themethod of claim 29, wherein the execution information is utilized forremote execution of the application in the second device.
 31. The methodof claim 26, wherein the second device comprises CEA-2027A or CEA-931Bmiddleware that utilizes XHT technology.
 32. The method of claim 31,wherein the second device comprises at least one High Definition AudioVideo Network Alliance digital television.
 33. The method of claim 26,wherein the executing the application, comprises managing at least oneof download of the application, the execution of the application in thesecond device, and termination of the execution of the application inthe second device.
 34. The method of claim 26, wherein the requestcomprises a request for channel tuning for the application or a requestfor at least one of an MPEG transport stream, system information data,and program system information data.